System having a protocol independent configuration environment

ABSTRACT

A system and approach that may provide a protocol independent environment to configure an ASC (application specific control) device in, for example, a heating, ventilation and air conditioning system. By using this system and approach, a user may reuse a device configuration already done for a device of one protocol in a device of another protocol without being required to reconfigure the latter device from scratch. This way may help a user to reduce the total setup time required to fully configure a device. The reduction may be done by simply exporting the configuration information from the first device and then importing the configuration information into the second device, where the internal protocol specific details can be handled internally by a tool. Thus, a user need not bother with the details that are in the background of the moving a configuration among devices of different protocols.

BACKGROUND

The present disclosure pertains to device configurations in view ofvarious protocols.

SUMMARY

The disclosure reveals a system and approach that may provide a protocolindependent environment to configure an ASC (application specificcontrol) device in, for example, a heating, ventilation and airconditioning system. By using this system and approach, a user may reusea device configuration already done for a device of one protocol in adevice of another protocol without being required to reconfigure thelatter device from scratch. This way may help a user to reduce the totalsetup time required to fully configure a device. The reduction may bedone by simply exporting the configuration information from the firstdevice and then importing the configuration information into the seconddevice, where the internal protocol specific details can be handledinternally by a tool. Thus, a user need not bother with the details thatare in the background of the moving a configuration among devices ofdifferent protocols.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 is a diagram of workbench palette;

FIG. 2 is a diagram showing a palette of variable air volume devices ofdifferent protocols in a station;

FIG. 3 is a diagram of a wizard based screen used to configure avariable air volume device of a first protocol;

FIG. 4 is a diagram of an enlarged view of a palette in the diagram ofFIG. 3;

FIG. 5 is a diagram of an enlarged view of a wizard in the diagram ofFIG. 3;

FIG. 6 is a diagram of a wizard based screen used to configure avariable air volume device of a second protocol;

FIG. 7 is a diagram of an enlarged view of a palette in the diagram ofFIG. 6;

FIG. 8 is a diagram of an enlarged view of a wizard in the diagram ofFIG. 6;

FIG. 9 is a diagram of submenu for exporting a configuration from adevice of a first protocol;

FIG. 10 is a diagram of submenu for importing a configuration into adevice of a second protocol;

FIG. 11 is a diagram of an activity flow chart for a protocolindependent configuration environment;

FIG. 12 is a diagram of a further activity flow chart related to theflow chart of FIG. 11; and

FIG. 13 is a diagram of an illustrative example of a layout of thepresent system.

DESCRIPTION

The present system and approach may incorporate one or more processors,computers, controllers, user interfaces, wireless and/or wireconnections, and/or the like, in an implementation described and/orshown herein.

This description may provide one or more illustrative and specificexamples or ways of implementing the present system and approach. Theremay be numerous other examples or ways of implementing the system andapproach.

Reference may be made to symbols in the drawing. Symbols may havevirtually any shape (e.g., a block) and may designate hardware, objects,activities, steps, procedures, and other items.

Some solutions that may be of concern incorporate a protocol independentenvironment to configure an ASC (application specific control) in HVAC(heating, ventilation and air conditioning) controllers. The protocolindependent environment may help a user reduce a total setup time neededto fully configure, for example, a VAV (variable air volume) device.Other kinds of devices may also be configured in such an environment.

The present system and approach may provide the protocol independentenvironment to configure an ASC in an HVAC. By using the system andapproach, a user may reuse the device configuration, already done forthe Lon Stryker VAV device, in a BACnet Stryker VAV device without beingrequired to reconfigure the device from scratch. This way may help auser to reduce the total setup time required to fully configure aStryker VAV device. The reduction may be done by simply exporting theconfiguration information from the Lon Stryker VAV device and thenimporting the configuration information into the BACnet Stryker VAVdevice, where the internal protocol specific details are handledinternally by a tool. A user need not bother with the details that arein the background of moving a configuration.

The following items reveal a workflow of the present approach. A usermay see the Honeywell Stryker™ devices, as illustrative devices, under aNiagara™ workbench palette 11 in FIG. 1 that can be added into Niagarastation and commissioned with the actual controller and be used. AStryker device may be a controller. Palette 11 may show “CompanyAsc” asa title in space 40 and show a listing of devices entitled “AscLonVAV”,“AscLonCVAHU” and “AscBacnetVAV”, in lines 41, 42 and 43, respectively.The user may need to add Lon™ or BACnet™ network under a Niagara stationat line 45 of palette 44 in order to use the Lon Stryker VAV or BACnetStryker VAV devices in the station as shown in a diagram 12 of FIG. 2. Ahost may be noted at line 45 and a station at line 46 of palette 44. Astation of line 46 may be a Niagara station. Below line 46 may be aconfiguration line 47 and drivers at line 48. A Niagara network may belisted at line 49. A Lon network in the Niagara station may be listed atline 50. Listed under the Lon Network at line 50 may be AscLonVAV thatmay be a Lon Stryker VAV device at line 52. Listed under the drivers atline 48 may be a BACnet network in Niagara station at line 53. Listedunder the BACnet network at line 53 may be AscBacnetVAV that is a BACnetStryker VAV device at line 58. AscLonVAV of line 52 may be noted on line41 of palette 11 of FIG. 1. AscBacnetVAV of line 58 of FIG. 2 may benoted on line 43 of palette 11. The term “palette” used in the presentdescription may be substituted with another term such as a “navigation(nav) tree”, “tree”, “menu”, or another like term.

The user may have a wizard based screen 13 to configure the Lon StrykerVAV device as shown in FIG. 3. Screen 13 may incorporate a palette 61and a VAV configuration wizard 62. A visual enlargement of palette 61 isshown in FIG. 4. Palette 61 may resemble palette 44 in FIG. 2. Afeatured item may be an AscLonVAV (Lon Stryker VAV device) at line 52 ofpalette 61.

An enlarged view of wizard 62 is shown in FIG. 5. One instance ofsettings in a menu for a configuration of a VAV may indicate acontroller type with an actuator at an entry 63, a pressure type at anentry 64, a box type of a single duct at an entry 65, a normal flow typeat an entry 66, a Honeywell model TR71/75™ wall module type at an entry67, a controller power up disable time of 10 seconds selected from arange of 1 to 300 seconds at an entry 68, and a set time during adownload at an entry 69. Entries 63-68 may have other selections thanthose shown. An entry 69 may have an entry of a set time during downloaddespite a present absence of it. Entries 71 may be for daylight savingssettings. Other settings may be indicated at a column in an area 73 ofwizard 62. Such settings, for example, may incorporate VAV outputs, VAVinputs, temperature setpoints, flow setpoints, control parameters,schedule, PID, accessory loops, custom wiring, and possibly more items,depending on a kind of device one has and its properties.

The user may have a similar wizard based screen 14 as like a Lon StrykerVAV device to configure the BACnet Stryker device while hiding theprotocol specific details from the user as shown in FIG. 6. Screen 14may incorporate a palette 75 and VAV configuration wizard 76. Anenlarged view of palette 75 is shown in FIG. 7. Palette 75 may resemblepalettes 44 and 61 in FIGS. 2 and 4, respectively. A featured item isAscBacnetVAV (BACnet Stryker VAV device) at line 58.

An enlarged view of wizard 76 is shown in FIG. 8. An instance ofsettings of a VAV may indicate a controller type with an actuator at anentry 77, a pressure type at an entry 78, a box type of a single duct atan entry 79, a normal flow type at an entry 81, a model TR71/75™ wallmodule type at an entry 82, a controller power up disable time of 10seconds selected from a range of 1 to 300 seconds at an entry 83, and aset time during a download at an entry 84. Entries 77-79 and 81-83 mayhave other selections than those shown. An entry 84 may have a set timeduring download despite a present absence of it. Entries 85 may be fordaylight savings settings. Other settings may be indicated at a columnin an area 87 of wizard 76. Such settings, for example, may incorporateVAV outputs, VAV inputs, temperature setpoints, flow setpoints, controlparameters, schedule, PID, accessory loops, custom wiring, and possiblymore items, depending on what kind of device that one has and itsproperties. Wizard 76 may be similar to wizard 62 and be like a LonStryker VAV device to configure a BACnet Stryker device in that thespecific protocol details are hidden from a user. Incidentally, areversal of the approach may also be utilized.

A user who already has the Lon Stryker VAV device may need to use theBACnet Stryker VAV device in the same job or in a different job similarto the Lon Stryker VAV device need not have to reconfigure the BACnetStryker VAV device from scratch; instead the user may export the currentconfiguration available in Lon Stryker VAV device into the BACnetStryker VAV device.

One may click on AscLonVAV at line 52 of diagram 15 of palette 61 to geta submenu 91 in FIG. 9 that shows items of views, actions, download,upload, export and import. One may click on an “Export” nomenclature 92to export a configuration from a Lon Stryker VAV device. Then one mayclick on AscBacnetVAV at line 58 of diagram 16 of palette 75 to get asubmenu 95 in FIG. 10 that shows items of views, actions, download,upload, export and import. One may click on an “Import” nomenclature 96to import the configuration into BACnet Stryker VAV device. One may alsoreuse the configuration from the BACnet Stryker VAV device into a LonStryker VAV device. In a similar manner, one may export a configurationfrom the BACnet Stryker VAV device and then import it into the LonStryker VAV device.

FIG. 11 is a diagram of an activity flow chart 20 for a protocolindependent configuration environment. Symbol 21 may indicate creating acomponent to define a LON or BACnet type of device. Under the device maybe a defining of generic data points to store NV (networkvariable/object) values, as noted in symbol 22. The generic data pointsmay be used to hide a network variable/object interface configurationfrom a user, as indicated by symbol 23. In symbol 24, the user mayconfigure the generic points for a VAV box configuration.

Symbol 25 may indicate that a software tool can handle a conversion orpropagation of values from generic data points to network variableshiding a complexity from the user. The user may now export a data/valuefrom the generic data points defined in the device, and a software toolmay have an option to export the data, as noted in symbol 26.

The software tool may also provide internal mapping of the generic datapoints to actual network variables/objects based on a purpose of theconfiguration, as indicated by symbol 27. The software tool may have anoption to import the data back into the LON/BACnet devices, as noted atsymbol 28.

FIG. 12 is a diagram of an activity flow chart 30 that may be related toflow chart 20 in FIG. 11. Since the generic data points are commonbetween Lon and BACnet, values may be updated to a matching data pointto a target device while importing data, as indicated by symbol 31.Symbol 32 notes that software may be used to update the value to theactual network variable/object once the data are imported, so that thedevice may propagate network specific values using an intended networkvariable/object managed by the software tool.

FIG. 13 is a diagram of hardware that may be, for example, VAVs oranother kind of devices revealing an export of a configuration by onedevice of one protocol and an import of the configuration by anotherdevice of another protocol, without internal protocol specific detailsbeing apparent to a user. The internal specific details may be handledby a tool.

For instance, a hardware device A 101 of a first protocol may export aconfiguration C along a path 103 that is imported by a hardware device B102 of a second protocol. Configuration C may in turn be exported fromhardware device B 102 along a path 104 to be imported by hardware deviceA 101.

To recap, a protocol independent mechanism may incorporate a firstdevice having a first protocol, a second device having a secondprotocol, and generic data points defined under the first device tostore network variable values. The first device may have a configurationthat is conveyed to the second device. The generic data points may hidea network variable interface configuration from a user.

The generic data points may be configured for the first device. Valuesfrom the generic data points may be converted to network variables tohide complexity due to internal protocol specific details which areprocessed internally by a processor at the first device.

The values from the generic data points configured for the first devicemay be exported.

The generic data points may be mapped to the network variables.

The values from the generic data points that are exported may beimported by the second device.

The values may be exported by the second device and be imported by thefirst device.

An approach in a protocol independent configuration environment, mayincorporate defining a first component having a first protocol, defininga second component having a second protocol, defining generic datapoints under the first component to store network variable values,hiding a network variable interface configuration from a user with thegeneric data points, configuring the generic data points for a firstcomponent configuration, converting values from the generic data pointsto network variables, and exporting values from the generic data pointsdefined in the first component.

The values from the generic data points defined in the first componentmay represent a configuration of the first component.

The approach may further incorporate importing the configuration of thefirst component to the second component.

The approach may further incorporate mapping the generic data points tonetwork variables.

The approach may further incorporate importing the configuration back tothe first component from the second component.

The approach may further incorporate updating values of the networkvariables upon importing the configuration to the second component.

The first protocol may be LON. The second protocol may be BACnet. Thefirst and second components may be VAV boxes.

A system having a protocol independent configuration environment mayincorporate a first component that defines a first protocol device, anda second component that defines a second protocol device. Generic datapoints may be defined under the devices to store network variablevalues.

The generic data points may be used to hide a network variable interfaceconfiguration from a user.

The generic data points may be configured for a device configuration bya user.

There may be a conversion or propagation of values from the generic datapoints to network variables while hiding specific protocol details froma user.

The values from the generic data points defined under one device may beexported by a user.

Internal mapping of the generic data points to the network variables mayoccur based on a purpose of the network variable interface configurationto hide the specific protocol details from the user.

The values of the generic data points defined in the device may beimported into another device.

Generic data points may be common between the first protocol and thesecond protocol. The values from the generic data points of a deviceexporting configuration information may be used to update the values ofmatching generic data points of a device importing the configurationinformation.

The values of the network variables may be updated upon importing theconfiguration information to the device.

One protocol of the first and second protocols may be LON. Anotherprotocol of the first and second protocols may be BACnet. The devicesmay be VAV boxes of an HVAC system.

U.S. Pat. No. 8,793,668, issued Jul. 29, 2014, is hereby incorporated byreference. U.S. Pat. No. 8,640,120, issued Jan. 28, 2014, is herebyincorporated by reference.

Any publication or patent document noted herein is hereby incorporatedby reference to the same extent as if each publication or patentdocument was specifically and individually indicated to be incorporatedby reference.

In the present specification, some of the matter may be of ahypothetical or prophetic nature although stated in another manner ortense.

Although the present system and/or approach has been described withrespect to at least one illustrative example, many variations andmodifications will become apparent to those skilled in the art uponreading the specification. It is therefore the intention that theappended claims be interpreted as broadly as possible in view of therelated art to include all such variations and modifications.

What is claimed is:
 1. A protocol independent mechanism comprising: afirst device having a first protocol; a second device having a secondprotocol; and generic data points defined under the first device tostore network variable values; and wherein: the first device has aconfiguration that is conveyed to the second device; and the genericdata points hide a network variable interface configuration from a user.2. The mechanism of claim 1, wherein: the generic data points areconfigured for the first device; and values from the generic data pointsare converted to network variables to hide complexity due to internalprotocol specific details which are processed internally by a processorat the first device.
 3. The mechanism of claim 2, wherein the valuesfrom the generic data points configured for the first device areexported.
 4. The mechanism of claim 3, wherein the generic data pointsare mapped to the network variables.
 5. The mechanism of claim 4,wherein the values from the generic data points that are exported areimported by the second device.
 6. The mechanism of claim 5, wherein thevalues can be exported by the second device and be imported by the firstdevice.
 7. A method in a protocol independent configuration environment,comprising: defining a first component having a first protocol; defininga second component having a second protocol; defining generic datapoints under the first component to store network variable values;hiding a network variable interface configuration from a user with thegeneric data points; configuring the generic data points for a firstcomponent configuration; converting values from the generic data pointsto network variables; and exporting values from the generic data pointsdefined in the first component.
 8. The method of claim 7, wherein thevalues from the generic data points defined in the first componentrepresent a configuration of the first component.
 9. The method of claim8, further comprising importing the configuration of the first componentto the second component.
 10. The method of claim 9, further comprisingmapping the generic data points to network variables.
 11. The method ofclaim 9, further comprising importing the configuration back to thefirst component from the second component.
 12. The method of claim 10,further comprising updating values of the network variables uponimporting the configuration to the second component.
 13. The method ofclaim 9, wherein: the first protocol is LON; the second protocol isBACnet; and the first and second components are VAV boxes.
 14. A systemhaving a protocol independent configuration environment comprising: afirst component that defines a first protocol device; and a secondcomponent that defines a second protocol device; and wherein genericdata points are defined under the devices to store network variablevalues.
 15. The system of claim 14, wherein: the generic data points areused to hide a network variable interface configuration from a user; andthe generic data points are configured for a device configuration by auser.
 16. The system of claim 15, wherein: there is a conversion orpropagation of values from the generic data points to network variableswhile hiding specific protocol details from a user; and the values fromthe generic data points defined under one device are exported by a user.17. The system of claim 16, wherein: internal mapping of the genericdata points to the network variables occur based on a purpose of thenetwork variable interface configuration to hide the specific protocoldetails from the user; and the values of the generic data points definedin the device are imported into another device.
 18. The system of claim16, wherein: generic data points are common between the first protocoland the second protocol; and the values from the generic data points ofa device exporting configuration information are used to update thevalues of matching generic data points of a device importing theconfiguration information.
 19. The system of claim 18, wherein thevalues of the network variables are updated upon importing of theconfiguration information to the device.
 20. The system of claim 18,wherein: one protocol of the first and second protocols is LON; anotherprotocol of the first and second protocols is BACnet; and the devicesare VAV boxes of an HVAC system.